Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: Use tox rng to seed the keypair generation. #2671

Merged
merged 1 commit into from
Feb 11, 2024

Conversation

iphydf
Copy link
Member

@iphydf iphydf commented Feb 9, 2024

Fixes #2649


This change is Reviewable

@iphydf iphydf added this to the v0.2.19 milestone Feb 9, 2024
@iphydf iphydf marked this pull request as ready for review February 9, 2024 22:57
Copy link

codecov bot commented Feb 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (961891d) 73.02% compared to head (5d7b7a7) 73.02%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2671      +/-   ##
==========================================
- Coverage   73.02%   73.02%   -0.01%     
==========================================
  Files         148      148              
  Lines       30482    30484       +2     
==========================================
+ Hits        22261    22262       +1     
- Misses       8221     8222       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@iphydf iphydf force-pushed the rng-sign-keypair branch 2 times, most recently from d88a13c to ac63bce Compare February 9, 2024 23:58
@Green-Sky
Copy link
Member

this makes key generation deterministic. Did you check how the fuzzer behaves with this?

@iphydf
Copy link
Member Author

iphydf commented Feb 10, 2024

What behaviour do you want me to check regarding the fuzzer?

@Green-Sky
Copy link
Member

Sorry, my real question was: "Is this intentional, with all its side effects" :)

@iphydf
Copy link
Member Author

iphydf commented Feb 10, 2024

Yes, it is intentional to make tests and fuzzers deterministic.

Copy link
Member

@JFreegman JFreegman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 5 of 5 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: :shipit: complete! 2 of 1 approvals obtained

@toktok-releaser toktok-releaser merged commit 5d7b7a7 into TokTok:master Feb 11, 2024
60 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

create_extended_keypair should use Random and be made deterministic for fuzzing
5 participants